Skip to content

fix: Add SafeArea insets to onboarding screen#406

Open
Egge21M wants to merge 1 commit into
cashubtc:masterfrom
Egge21M:safearea-onboarding
Open

fix: Add SafeArea insets to onboarding screen#406
Egge21M wants to merge 1 commit into
cashubtc:masterfrom
Egge21M:safearea-onboarding

Conversation

@Egge21M

@Egge21M Egge21M commented Feb 3, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

@Egge21M Egge21M linked an issue Feb 3, 2026 that may be closed by this pull request
const { t } = useTranslation([NS.common]);
const [accepted, setAccepted] = useState(false);
const insets = useSafeAreaInsets();
const bottomInset = Platform.OS === "android" ? insets.bottom : 0;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That didn't resolve it. I added 60 to the bottomInset and that moved it up enough. That also lets us skip wrapping it in the view below.

const bottomInset = Platform.OS === "android" ? 60 + insets.bottom : 60;

/>
<TouchableOpacity
<View style={[styles.container, { paddingBottom: bottomInset }]}>
<Onboarding

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can remove the view wrap and add

      bottomBarHeight={bottomInset}

above the onDone call

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[UI Bug] Setup "Next" button hidden under Android navigation bar

2 participants